<?php
/**
 * <https://y.st./>
 * Copyright © 2015 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. Sf not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'title' => 'The Kingdom of Tonga',
	'body' => <<<END
<p>
	I spent most of the day preparing for tomorrow by scoping out the local mall and writing up a resume.
	My resume isn&apos;t great, but it&apos;s better than nothing and I&apos;ve been jobless far too long.
</p>
<p>
	Before heading off to bed, I wanted to make at least a little progress on my $a[ccTLD] research, so I decided to check registries until I found a single registry that allowed registration without a telephone number.
	It only took two tries to find such a registry: the registry running the $a[ccTLD] of the <a href="/en/URI_research/ccTLDs.xhtml#to">Kingdom of Tonga</a>.
	Their registration form doesn&apos;t ask for a telephone number, not even in the section that takes credit card information.
	I found this quite odd because I&apos;ve never seen a credit card information form that did not require a telephone number; I simply though that the credit card processing protocol required this.
	I always entered a fictitious number and Discover, not having a telephone number on file for me to match it against, processed the transaction without problems.
</p>
<p>
	It appears that here is a <a href="http://to/">website run on the $a[TLD] itself</a>.
	I knew this was technically possible, I just didn&apos;t know anyone was actually doing it.
	The strange thing though is that the webserver that serves this website is sending a default, unconfigured website without any content.
	Aside from the lack of content, this is actually something I want to do someday myself.
	Once I&apos;m doing a lot better financially, I want to acquire my own three-character $a[TLD].
	Alternatively, if someone has acquired a single-character $a[TLD] by that time, I wouldn&apos;t mind instead acquiring a single-character $a[SLD] under their $a[TLD].
	After that, of course, I would aim to try to become the manager of a second-level domain.
	This would be a precarious position for me to be in though, if I stupidly gave up both my three-character name and this name.
	I am not a country, nor will I ever be.
	I also don&apos;t have what it takes to lead a country.
	If I end up in control of a $a[ccTLD], it will be in a partnership in which I have offered to try to increase profits for whatever country I have partnered with.
	They could end the partnership at any time.
	Likewise, I would be required to sell domains, not keep the name space to myself.
	I might be able to put a website at the $a[TLD] itself, but aside from that, the domain would be in pieces, sold to any willing buyer.
	Next, I would want to control a single-character domain.
	If I recall, $a[IANA] said something about single-character $a[TLD]s being reserved for uses that would benefit the public well.
	Again, me having a personal name space doesn&apos;t really accomplish anything for the public, so I wouldn&apos;t in any realistic situation be able to actually own and control a single-character $a[TLD].
	Stepping even further in this fantasy, the final step would be to take control of $a[IANA] and the root name space: <code>.</code>.
	At this point, everything pretty much falls apart on a technical level.
	Forgetting the sheer impossibility of getting enough authority to make this happen, if I control all the names, names become useless.
	No one will have $a[DNS] names besides me, so no one will use $a[DNS].
	Besides, I don&apos;t want to have a monopoly on names, that would just be evil.
	That is, unless someone creates a new $a[DNS] root, in which case, I immediately lose everything.
	And do all protocols even work using the root domain? The $a[HTTPS] $a[URI] scheme is &quot;https://{domain without trailing dot}{path}&quot;.
	A website at the root domain would therefore have a $a[URI] of <code>https:///</code>.
	Would the triple slash mean that the website was hosted at the root domain, or would it be an invalid $a[URI] that didn&apos;t even specify a host? If I decided not to encrypt things, <code>http://./</code> would be a completely-valid $a[URI], but a lack of encryption isn&apos;t safe.
</p>
<p>
	In any case, fantasies can be fun, even if I do over-analyze them to the point where they become incoherent and fall apart.
</p>
<p>
	My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
</p>
END
);
